Skip to content

Conversation

@Shreyas281299
Copy link
Contributor

@Shreyas281299 Shreyas281299 commented Jan 9, 2026

COMPLETES # https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7498

This pull request addresses

If an error occured during registration the sdk was not throwing the error and widgets wernt handling the error properly causing the app to be stuck in the loading screen

by making the following changes

  • Updated the SDK version with proper error being thrown
  • Handled error that might happen when cc.register is invoked

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • Blocked the subscribe url to throw error in the SDK, checked that the widgets are not stuck in an endless loading screen
Screen.Recording.2026-01-09.at.1.00.11.PM.mov

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document
  • I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

@aws-amplify-us-east-2
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-590.d1b38q61t1z947.amplifyapp.com

init(options: InitParams): Promise<void> {
return this.store.init(options, this.setupIncomingTaskHandler);
return this.store.init(options, this.setupIncomingTaskHandler).catch((error) => {
const err = error instanceof Error ? error : new Error(String(error));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
const err = error instanceof Error ? error : new Error(String(error));
const err = error instanceof Error
? error
: new Error(`Store initialization failed: ${String(error)}`);

module: 'cc-store#store.ts',
method: 'init',
webex.once('ready', () => {
setupEventListeners(webex.cc);
Copy link
Contributor

@bhabalan bhabalan Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If setupEventListeners throws, we aren't doing a clearTimeout. Should we wrap the body of the entire arrow function inside a try catch and clear the timeout if anything happens and reject?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants